Skip to content

Drop python3.13t#2684

Draft
mayeut wants to merge 3 commits intopypa:mainfrom
mayeut:drop-python3.13t
Draft

Drop python3.13t#2684
mayeut wants to merge 3 commits intopypa:mainfrom
mayeut:drop-python3.13t

Conversation

@mayeut
Copy link
Member

@mayeut mayeut commented Dec 6, 2025

Draft
towards #2683

This PR combines the 3 commits that might be split differently.
My preference would be 1st commit (deprecation) then combine the last 2 commits (removal of cp313t and the corresponding enable option).
Other possible options I see:

  • deprecate only as a pinned issue and combine the deprecation commit/cp313t removal commit, remove the option later.
  • deprecate only as a pinned issue and keep this PR as-is
  • tell manylinux not to remove cp313t

@mayeut mayeut added the Hold for future release This PR might be complete, but is scheduled to be merged in a future release. Don't merge yet. label Dec 6, 2025
mayeut added 3 commits March 5, 2026 22:37
Free-Threading Python 3.13 was experimental.
Now that Python 3.14 has been released with explicit support, we can schedule removal of Python 3.13 free-threading.
@mayeut mayeut force-pushed the drop-python3.13t branch from 711ff25 to 74e1712 Compare March 5, 2026 21:39
@mayeut
Copy link
Member Author

mayeut commented Mar 7, 2026

@joerick, @henryiii, any thoughts on deprecation ?
For python 3.13t, I think users can start dropping right now for the reasons outlined in #2683 (comment) so we could start issuing the deprecation early on (which might not be a good idea for python 3.8 in #2686 yet).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Hold for future release This PR might be complete, but is scheduled to be merged in a future release. Don't merge yet.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant